Skip to content

Update ghcr.io/flamingo-stack/registry/mongo Docker tag to v8.3.4#33

Open
ivan-flamingo wants to merge 1 commit into
masterfrom
renovate/ghcr.io-flamingo-stack-registry-mongo-8.x
Open

Update ghcr.io/flamingo-stack/registry/mongo Docker tag to v8.3.4#33
ivan-flamingo wants to merge 1 commit into
masterfrom
renovate/ghcr.io-flamingo-stack-registry-mongo-8.x

Conversation

@ivan-flamingo

@ivan-flamingo ivan-flamingo commented Jun 9, 2026 •
edited
Loading

Copy link
Copy Markdown

This PR contains the following updates:

Package Update Change
ghcr.io/flamingo-stack/registry/mongo (source) minor 8.0.9 → 8.3.4

Configuration

📅 Schedule: (UTC)

  • Branch creation
    • At any time (no schedule defined)
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

  • If you want to rebase/retry this PR, check this box

This PR has been generated by Mend Renovate.

@coderabbitai

coderabbitai Bot commented Jun 9, 2026 •
edited
Loading

Copy link
Copy Markdown

Review Change Stack

Warning

Review limit reached

@ivan-flamingo, we couldn't start this review because you've reached your PR review rate limit.

More reviews will be available in 49 minutes. Learn how PR review limits work.

To continue reviewing without waiting, enable usage-based billing in the billing tab.

⌛ How to resolve this issue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based credits.

🚦 How do rate limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please see our Fair Usage Limits Policy for further information.

ℹ️ Review info
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: 5d02f62d-2711-4e31-aabf-54b42da4a068

📥 Commits

Reviewing files that changed from the base of the PR and between b5326c3 and 7432edf.

📒 Files selected for processing (1)
  • charts/meshcentral/values.yaml
📝 Walkthrough

Walkthrough

This pull request updates the MeshCentral Helm chart to use container image version 8.3.4 instead of 8.0.9 in the charts/meshcentral/values.yaml configuration file.

Changes

MeshCentral Version Update

Layer / File(s) Summary
Image tag version bump
charts/meshcentral/values.yaml		 The initImage block tag value is updated from 8.0.9 to 8.3.4.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Poem

🐰 From eight to three-point-four we leap,
A version upgrade, swift and steep,
The Helm chart nudges, small but true,
MeshCentral springs with shiny new! ✨

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title accurately reflects the main change: updating a Docker image tag from 8.0.9 to 8.3.4 in the meshcentral Helm chart.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch renovate/ghcr.io-flamingo-stack-registry-mongo-8.x

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@ivan-flamingo ivan-flamingo force-pushed the renovate/ghcr.io-flamingo-stack-registry-mongo-8.x branch from 31f06b6 to b5326c3 Compare June 14, 2026 03:53
@ivan-flamingo ivan-flamingo changed the title Update ghcr.io/flamingo-stack/registry/mongo Docker tag to v8.3.2 Update ghcr.io/flamingo-stack/registry/mongo Docker tag to v8.3.4 Jun 14, 2026
@ivan-flamingo ivan-flamingo force-pushed the renovate/ghcr.io-flamingo-stack-registry-mongo-8.x branch 2 times, most recently from d5dc347 to 06b93b2 Compare June 17, 2026 11:24
@ivan-flamingo ivan-flamingo force-pushed the renovate/ghcr.io-flamingo-stack-registry-mongo-8.x branch 2 times, most recently from 02406e3 to 96cc9d7 Compare June 24, 2026 19:20
@ivan-flamingo ivan-flamingo force-pushed the renovate/ghcr.io-flamingo-stack-registry-mongo-8.x branch from 96cc9d7 to 7432edf Compare June 25, 2026 21:19
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

2 participants

@ivan-flamingo @renovate-bot